@butler54 I completely agree that using trestle here is a good opportunity. I want to link the CNCF design proposal example. I think we could tailor this for the template. What you have already lines up well. I would recommend adding Goals, Non-Goals, and Impact/Key Questions.

Editing my recommendation: You already have Definition of Done, so maybe adding Scope to communicate Non-Goals. WDYT?

@jpower432 / @jflowers - I've made an incremental change, however, looking at the CNCF design proposal template. I think we should faithfully recreate it. Why: It gives us a bit of a springboard to a long term goal: trestle, by default, is expected by the CNCF to be use used to enforce templates (maybe I am being ambitious).

if we agree this is a good idea moving forward I'll translate it into the proposal template @jpower432's referenced with a few tweaks (I would like to see the metadata stored as a a yaml header).

if we agree this is a good idea moving forward I'll translate it into the proposal template @jpower432's referenced with a few tweaks (I would like to see the metadata stored as a a yaml header).

@butler54 I am on board with this. The template we have is almost as comprehensive as the CNCF design proposal template so we might as well align on the naming of the sections for consistency/reuse. Another example of a good comprehensive template is Kubernetes Enhancements.

I like it! I think it's a good ambition.

Okay this should be good to review now / ready to roll.

As mentioned in the document the project will need to be updated to mandate trestle author docs validate passing.

It's good to be merged now based on your feedback.